Please enable JavaScript to view this website.

Skip to main content

BLE Module Initialization

This page covers Phase 4 — BLE module preparation and writing. It is called from the OpenLink initialization path and applies to M18, M12, MX, and embedded-tick products that carry a BLE module with unique identity support.

Phase 4 — BLE Module Preparation & Write​

4a. Determine module type​

  1. Read the BLE module type. On failure, retry once.
  2. If still unreadable: for an MX tool/battery that was originally a BLE113, override the type to BLE113; otherwise propagate the error.
  3. Wrong-kit guard: if the tool record indicates a linked BLE record exists but the connected module reports BLE113, abort with a "wrong service kit installed" error.
  4. If the module is BLE113 (no unique identity support), stop here — nothing to write.

4b. Capability detection (BGM11S / BGM220 / BGM13S)​

  1. Read the BLE firmware version. If it reports Unknown, abort.
  2. Determine encryption support:
    • BGM220 and BGM13S: always supported.
    • BGM11S: supported only if firmware ≥ 5.1.0.0.

4c. Obtain the BLE context (identity to write)​

  • If the tool record already carries a BLE context, use it — but:
    • It must contain a unique MPBID and all four passwords plus a BOD, or abort.
    • If encryption is supported but the MLS certs are missing or invalid, unlink the existing BLE record from the tool (cloud) and provision a fresh one (see BLE provisioning).
  • Else if a cached provision record exists in the local cache for this tool MPBID, use it.
  • Else provision a new BLE record (see BLE provisioning).

4d. Write BLE initialization data​

  1. Establish METCO access on the module: try the default METCO password first. If that fails, try the METCO password from the BLE context. If that also fails, read the module's current MPBID, fetch that MPBID's tool record from the cloud, and try its METCO password. If all fail, abort.
  2. Write, in order:
    1. BLE MPBID
    2. BLE METCO Password
    3. BLE User Password
    4. BLE Admin Password
    5. BLE Service Password
    6. BLE Born-On-Date
    7. Set the BLE real-time clock to the current Unix time (seconds).
  3. Product-specific BLE thresholds (low-pack ADC thresholds, written as 16-bit hex):
    • One-inch D-handle impact wrench: ADC1 = 095C, ADC2 = 08C6, ADC3 = 095C.
    • Digital torque wrench: ADC1 = ADC2 = ADC3 = 0967.
  4. If an ownership claim key is present, write it to the module.
  5. MLS certificates (only if all four cert artifacts are present):
    • Validate each artifact has an even-length hex string; abort if not.
    • Erase existing security certificates.
    • For each of the following, write a 4-byte size/count to the size segment, then write the cert payload (payload is written in two parts across paired memory segments):
      1. Public Root Cert
      2. Public Intermediary Cert
      3. Public Device Cert
      4. Private Device Raw Key (size, then the raw key)

4e. BLE provisioning (when a fresh record is needed)​

  1. Manufacturing: provision a new record using the product ID for the module type, requesting certs only if encryption is supported. Product IDs by module:
    • BGM11S → 0x00A1
    • BGM220 → 0x014F
    • BGM13S → 0x0192
  2. Cloud: link the new BLE record to the tool (tool MPBID + module MPBID).
    • If linking fails because the tool MPBID is "not found": import the tool record (MPBID, all four passwords, BOD), then retry the link with exponential backoff — up to 5 attempts, waiting 1s, 2s, 4s, 8s, 16s before successive attempts. If all fail, abort with the last error.
    • Any other link error is propagated immediately.
  3. Cache the provisioned BLE record (keyed by tool MPBID) in the local cache for reuse.